feat: Add hooks #1218
feat: Add hooks #1218
Conversation
aawsome
force-pushed
the
hooks
branch
2 times, most recently
from
50d670e
to
720307a
Compare
| rustic_backend = { git = "https://github.com/rustic-rs/rustic_core.git", features = ["cli"] } | ||
| rustic_core = { git = "https://github.com/rustic-rs/rustic_core.git", features = ["cli"] } |
There was a problem hiding this comment.
I think we may want to release the changes first without re-introducing git dependencies again, changing them back later. Now that releasing should be just merging the release pr.
There was a problem hiding this comment.
If we wait for a release of rustic_core, we'll pile up PRs in rustic which depend on these things but cannot be merged. We won't have the features in the nightly builds and will not get any feedback until we release a rustic release.
As many changes in rustic are changes in rustic_core, I see no alternative than using a git dependency here.
There was a problem hiding this comment.
Ok, I understand. Do you think it would be viable to up the release cadence for rustic_core and say we do at least one release in a week with things that have been merged, even if small one's? It would be just a click away, we could release another rustic_core version today, for example.
This PR adds
run-before,run-after,run-failureandrun-finallyhooks for:[global]config profile sectionbackupcommand specifically in the[backup]config profile section[[backup.sources]]sectionNote: This PR includes only calling the given commands. If there is the wish for supplying information to the commands (env variables or parameter substitution), this should be covered by a separate feature request/PR.
closes #902